New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WIP] Elasticsearch upgrade #398
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
oalders
force-pushed
the
andreeap/elasticsearch-upgrade
branch
from
March 13, 2015 03:59
6338ed7
to
98e79f3
Compare
I was on the wrong repository and merged by accident this into the master, but I reverted the merge. |
I've fixed it now. Don't click any more merge buttons or push to master. :) You'll need to delete your master and grab the current version as your history is out of sync. |
Thank you, I was extremely scared for what I have done. |
This has mostly been moved to #405 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Making a PR so that review is a touch easier. Nicht mergen!
To use this branch you can do something like:
Not the most elegant way to do things, but it works and it'll be available when you run ./bin/prove without requiring any additional flags. Make sure you do a
carton install
orvagrant provision
after pulling in the changes.In order to run this on your VM:
To run the tests on your VM you'll (temporarily) need to use the "live" Elasticsearch instance. Keep in mind that doing this will blow away anything you may have previously indexed. We're still working on a fix for this.